x86/vvmx: Don't handle unknown nested vmexit reasons at L0
authorAndrew Cooper <andrew.cooper3@citrix.com>
Thu, 25 Oct 2018 13:11:58 +0000 (14:11 +0100)
committerAndrew Cooper <andrew.cooper3@citrix.com>
Tue, 30 Oct 2018 13:26:21 +0000 (13:26 +0000)
commitc238ea3f4caccf36ab1a559f958cbe5192327f6a
treec56fbb4d0fac37a02b9e0763694afda1c77f51a6
parent307ee30a1429e2f45d505c1299b58090edd81eb0
x86/vvmx: Don't handle unknown nested vmexit reasons at L0

This is very dangerous from a security point of view, because a missing entry
will cause L2's action to be interpreted as L1's action.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Sergey Dyasli <sergey.dyasli@citrix.com>
Acked-by: Kevin Tian <kevin.tian@intel.com>
xen/arch/x86/hvm/vmx/vvmx.c